Reset your password.
Use the secure link below. It expires in 15 minutes.
Reset passwordEMAIL PLATFORM FOR DEVELOPERS + AGENTS
Transactional, lifecycle, and campaign email through one API. Your agent handles routine operations. You control production.
Use the secure link below. It expires in 15 minutes.
Reset password
TRY IT IN YOUR BROWSER
Start fresh or bring the code you already have. Linnet turns either into a safe test send you can inspect.
Plain English is enough. Linnet will produce a typed request with the safety checks included.
Runs in Linnet test mode. No email reaches a real inbox.
Add an email description or paste a send call first.
PRODUCT / ACCOUNT
Use the secure link below. It expires in 15 minutes.
Reset password
The bird checked the boring parts.I classified this as transactional, added duplicate protection, and kept production sending off.
YOUR WEBSITE, NOW IN EMAIL
Enter your website. Linnet matches its look and feel, builds a complete email kit, and lets you review every choice.
WELCOME
Thanks for joining Whooshly. Your account is ready whenever you are.
Open your accountONE REQUEST, ONE TIMELINE
Every request returns a Message ID you can follow from acceptance through delivery, retries, or failure.
curl "$LINNET_API_URL/v1/emails" \
-X POST \
-H "Authorization: Bearer $LINNET_API_KEY" \
-H "Idempotency-Key: welcome-018f" \
-H "Content-Type: application/json" \
-d '{
"from": "Product <hello@yourdomain.com>",
"to": "person@example.com",
"subject": "Your workspace is ready",
"text": "Welcome aboard."
}'
FROM BRIEF TO READY-TO-SEND
Your agent turns a goal into an audience and message that are ready for your review. You see consent and exclusions before anything sends.
“Launch the autumn roast to repeat buyers. Keep the tone warm. Exclude anyone emailed this week.”
ONE API FOR EVERY EMAIL
Send transactional, lifecycle, and campaign email through one API while keeping the right checks for each kind of message.
Follow every request from acceptance to delivery.
Your code and your agent work from the same status.
Agents prepare changes. You decide what can run.
DELIVERY YOU CAN DEBUG
Let an agent handle routine email work without losing the checks developers expect.
See exactly what passed or failed across ownership, DKIM, SPF, and DMARC.
Exercise the request and event path without accidentally emailing real recipients.
Retry the same request without sending the email twice.
See acceptance, checks, attempts, and delivery results on one record.
Verify each event and see every retry when your endpoint is unavailable.
Give an agent only the tools it needs. Keep production access under your control.
REACH THE RIGHT HUMANS
Your agent handles repetitive campaign work. You can always see who will receive it, why they qualify, and who is excluded.
See why each person qualifies, who gave consent, and who is excluded.
An email address never quietly turns into permission to send.
Protect customers from overlapping campaigns and too many lifecycle emails.
Give the agent approved layouts, voice, and backup styles instead of a blank canvas.
Approve the actual message and recipients, not an earlier draft.
Campaigns, automations, consent, and delivery results stay connected.
MEET YOUR AI CREW
Assign routine work without sharing production keys or adding another system to manage.

Uses only the permissions it needs and never puts your key in the prompt.

Verifies signatures and retries failed webhook deliveries.

Finds the reason before anyone retries blindly.

Builds the segment and shows where every person came from.

Fits the message to the brief and the brand.

Coordinates the send. Still waits for your signal.
YOU STAY IN CONTROL
Linnet checks access, rules, and the latest account state before an agent can make a change.
Change the operation and the approval expires. That is the point.
INSIDE LINNET
Your code gets a predictable response. Your team gets the full timeline needed to debug a send without piecing together provider logs.


THE WORK BEHIND THE SEND
The polished message is only the surface. Linnet also shows what triggered it, whether the person can receive it, and when the journey stops.


START WITH ONE REAL SEND
Bring one use case. Validate the API, domain, and delivery trail in test mode before production traffic moves.